docs: Fix affected SDK version range for job-funneling troubleshooting - #769
Conversation
Correct the affected Runpod Python SDK version range in the Jobs
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| If your endpoint has multiple workers but nearly all jobs run on one worker while the others sit idle, and jobs stay `IN_QUEUE` even though workers are available, you may be running an affected version of the Runpod Python SDK. | ||
|
|
||
| Versions 1.9.1 through 1.10.0 could corrupt per-worker job tracking on endpoints that use a network volume, causing most workers to stop pulling new jobs. This most often appeared on network volume endpoints such as ComfyUI workers. | ||
| Versions 1.7.11 through 1.10.0 could corrupt per-worker job tracking on endpoints that use a network volume, causing most workers to stop pulling new jobs. This most often appeared on network volume endpoints such as ComfyUI workers. |
There was a problem hiding this comment.
Confirms affected version range for job-funneling bug: PR #517 states "Since SDK 1.7.11 ... Only 1.7.10 is unaffected," root-causes the network-volume-specific pickle-file mechanism (os.getcwd() shared mount), and fixes it. Released as v1.10.1 (compare v1.10.0...v1.10.1 per release PR #520), confirming v1.10.0 was the last broken version and 1.7.11 through 1.10.0 is the correct inclusive affected range.
Source: runpod/runpod-python#517
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.) |
1 participant
Open in Promptless
The "Jobs funneled to a single worker" troubleshooting section listed the affected Runpod Python SDK versions as "1.9.1 through 1.10.0." The job-distribution regression (fixed in runpod 1.10.1) actually began at version 1.7.11 — 1.7.10 was the last unaffected version. As written, a user on a 1.7.x or 1.8.x release hitting this exact symptom would wrongly conclude they were not affected and skip the upgrade.
This corrects the affected range to "1.7.11 through 1.10.0." It's a single-token fix; the network-volume framing, the ComfyUI example, and the "upgrade to runpod>=1.10.1" remedy were already accurate and are unchanged.
Files touched: serverless/troubleshooting.mdx
Trigger Events
Tip: Tag @Promptless in GitHub PR comments to guide documentation changes during code review 🐙